Guideline: How to Identify Configuration Items
This guideline purpose is to describe how how to Identify Configuration Items and what is the best moment to start controlling it.
Relationships
Related Elements
Main Description
Each and every file or set of files that are part of a product or project can be considered a configuration item (CI) in  terms of software configuration management and must be formally controlled.

But there are some criterias to define better what should be considered a configuration item, and what should not:

- Every item that needs to be contained in the release package should be considered as a CI.
- Every source file used to build the product or the component should be considered as a CI.
- Every document or source file that will serve as basis for future development should be considered as a CI.
- Anything that is an input to the process of creating your product should be controlled as a CI.

What not consider a configuration Item:

- Tools from outside the organization that are not expected to change over the course of the project should not be considered as CI.